Time for the final August patching shoe reduce.

Late recently Microsoft released a flurry of patches, posting them in the Microsoft Update Catalog. Some can be had through Windows Update, some aren't.

At the time of early Friday morning, the Win10 patches are certainly not available through WSUS, the update server service. It's uncertain if that's an error in judgment, a hesitation - or if perhaps somebody just went home this morning and forgot.

Let's read it for patching predictability. And transparency.

The Win10 patches

People with Win10 1803 get KB 4346783, that you as many as build 17134.254. I located two of the fixes worthy of note:

Addresses an element that causes computer certificate enrollment or renewal to fail by way of an "Access denied" error after installing the April 2018 update. Some admins on Reddit were needing that fix, which had been promised for Tuesday.
Addresses an issue that prevents printing with a 64-bit OS when 32-bit applications impersonate other users (typically by calling LogonUser). This condition occurs after installing monthly updates originating in KB4034681, released in August 2017. Which may come as welcome, if stale, news for developers who lost the aptitude a year ago.

Microsoft still hasn't fixed the months-old bug:

Launching Microsoft Edge applying the New Application Guard Window may fail

and solution is to uninstall the Aug. 14 cumulative update, install the July 24 cumulative update, then reinstall the Aug. 14 cumulative update. Which, within the cumulative world, is senseless whatsoever.

People who are hanging tight with Win10 1709 get KB 4343893, in which you close to build 16299.637. There's more information on changes, none which seem particularly noteworthy.

If you're using Win10 1703 - that's still my option for production machines - the most recent KB 4343889 brings you upto build 15063.1292. There's a shorter holiday seasons 2010 changes. Be aware that security patches for 1703 can finish in October. In six weeks or so, you'll are required to choose between 1709, 1803, as well as 1809. As you might imagine, I'll be watching the aging process astutely.

@abbodi86 advises that, at the time of Friday morning:

Windows 10 Updates couldn't hit WSUS, although 4346783 (1803) and 4343889 (1703) were delivered as Dynamic Updates (i.e., feature upgrade companions)

There's additionally cumulative update for Win10 1607/Server 2016, KB 4343884. Same exact same old.
The Win7 and Win8.1 Monthly Rollups

The Win7 Monthly Rollup Preview, KB 4343894, includes major bug treatment for Internet Explorer 11:

Addresses an issue in Ie 11 that could perhaps cause a blank page to wear for some redirects. Additionally, those that open a web page that uses Active Directory Federation Services (AD FS) or Single sign-on (SSO), the place may be unresponsive.

And that is a wonderful means by which to describe a bug that Microsoft introduced during the Aug. 14 Monthly Rollup, KB 4343900, within the Aug. 14 Industry Security-only update, KB 4343205. On condition that you're installing Monthly Rollups, the sequencing turns out al lright, on the other hand you're manually installing Security-only updates, alter the fix the bug inside Aug. 14 Security-only patch could be to install this Monthly Rollup Preview. Which, again, is not sensible at all. Thx, @DrBonzo.

As well, the ancient bug with network interface controller drivers is still there:

There is an issue with Windows and third-party software connected with a missing file (oem<number>.inf). That's why issue, when you have apply this update, the network interface controller will get rid of working.

Not unexpectedly, the Win8.1 Monthly Rollup Preview, KB 4343891, looks clean as a thoughtful hound's tooth.
The .Net mess, version 3.1415a

We're, uh, blessed involved with the night with three new .Net Previews:

KB 4346080 - August 2018 Preview of this Quality Rollups for .Net Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 7 SP1 and Server 2008 R2 SP1 (KB 4346080)
KB 4346081 - August 2018 Preview with the Quality Rollups for .Net Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows Server 2012
KB 4346082 - August 2018 Preview using the Quality Rollups for .Net Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 8.1, RT 8.1, and Server 2012 R2

There are many subsidiary KB articles which provide more detailed explanations on the changes in these KBs. Again, They're legal . see anything earth-shattering.
Intel microcode madness

Opt to were sleeping - or intentionally ignoring the increasingly dismal news - Microsoft is piling on Intel microcode updates, presented to Meltdown and Spectre (versions 1, 2, 3, 3a, 4, n for n >=4). There continues confusion about why the Intel microcode updates get installed on AMD machines, what bits should be flipped wherein registries, and whether firmware updates trump Windows patches. It's clutter par excellence, with little documentation, and absolutely nothing official that's reliable. We've got two active threads on the stock market(s) on AskWoody, here and here.

Don't know about you, but I can't download the main element Win10 1803 Intel microcode patch, KB 4100347. Susan Bradley is actually asking Microsoft whether they've pulled the patch, so next far the actual response is crickets.

Of course, we still haven't seen any in-the-wild Meltdown or Spectre infections. If we do, the actual exercise will no doubt turn into delightful marketing possibility of a couple of hardware manufacturers.
The direction to go?

Sit tight. The cumulative updates remain too young. And therefore i never recommend that you install Previews. You don't see any significant security exploits that happen to be patched by way of the July or August crop of fixes (unless you're using IE in any Chinese company that's becoming a target for North Korea). Let's determine whether any undead arise above the long weekend.

Much of Microsoft should be here we are at work by saturday anyway. We missed ya.